Geoida
Help
|
|
Geoida |
Data-related messages |
As Geoida is processing data, messages may be frequently displayed. Some of these messages may simply be for the user's information, others may be prompts for the user to make a decision which will affect the processing, while some messages may be to indicate that there are problems with the data requiring correction.
Many of the messages that appear will be self-explanatory, but the following table lists messages for which a more detailed explanation may be necessary.
| Message | Explanation |
| Are you SURE that you wish to clear ALL FIELDS ? | The Clear button was clicked - this function will clear all data fields on the currently displayed window page and all data will be lost. Answer NO to prevent clearing the data |
| Are you sure you wish to abandon current page and exit ? | The Cancel button was clicked - This function will discard any changes to the data currently displayed since it was last loaded or the current page displayed. Answer NO to return to the displayed data |
| Backsight point pppp has not been specified as Fixed | This point must be specified as FIXED at the start of a traverse |
| Cannot determine file type - check naming convention | Based on the name of the file, Geoida is trying to determine whether the file is an old-format or new-format CDS stadia file but cannot determine the type. Check that it is named correctly according to the CDS convention |
| Check file - less than 1 record | The data file is empty, corrupt, or is not the expected type of file and cannot be read (CDS stadia files) |
| Check library for valid Horizontal Datum entries | No valid records are stored for Geodetic Datum in the library - check that valid records exist or that Definitions.GLD has not been moved or deleted |
| Check library for valid Projection entries | No valid records are stored for Projection in the library - check that valid records exist or that Definitions.GLD has not been moved or deleted |
| Check library for valid Spheroid entries | No valid records are stored for Spheroid in the library - check that valid records exist or that Definitions.GLD has not been moved or deleted |
| Data error - cannot process Record nn in Page pp - check entries | One or more essential fields are blank while other fields contain valid data in the numbered record on the indicated page of data being processed. A record that is valid for the LS-Network adjustment option is not necessarily valid for the None or Bowditch adjustment options |
| Evaluation copy - please register to remove limitations | This message is displayed for an unregistered copy of Geoida. If it appears at any time subsequent to a previous validation, enter the validation details and code again |
| Failed to delete oldest database backup MyJob.~02
Reason - Path/file access error Cannot backup current job MyJob.gdb |
Before a second level (oldest) backup can be made, any existing backup at that level must be deleted. In this case deleting the file has failed, probably because it has previously been set to Read-Only by the user or has been opened by another application. This situation prevents a backup being made of the current job database until resolved |
| Failed to rename database backup MyJob.~01
Reason - Path/file access error Cannot backup current job MyJob.gdb |
To make a second level backup, any first-level backup must be renamed. In this case renaming the file has failed, probably because it has previously been set to Read-Only by the user or has been opened by another application. This situation prevents a backup being made of the current job database until resolved |
| File Filename does not exist | The file of the indicated name does not exist. If the filename was specified in some option by the user, check the spelling of the filename, the path selected, and that no illegal characters have been used such as * ? + < > | [ ] \ / , ; : ” +. To avoid the possibility of typing errors etc, it is preferable to choose the file by selection from a list if available |
| Height corr'n - single point only | This message may be displayed when reducing terrain-height distances to datum level during least squares adjustment. It indicates that there is no vertical component measurement available over this leg and that only one of the two end-points has a valid height. Because the true height of the mid-point cannot be computed, the single available height of one of the end-points is used |
| Horizontal Datum for this Projection is invalid | The record for the Geodetic Datum specified for the current Projection is invalid - check that record details are correct or that Definitions.GLD has not been moved or deleted |
| Input errors are suspected in data - tolerances exceeded. Do you wish to continue processing ? | One or more observation records may have been entered with mistakes - check the data. It could also simply indicate that the provisional point tolerance is too small and should be relaxed |
| Insufficient data in Extract file | There is not enough data in the file to permit the computation of any observation data - check the SDR or Traverse source data |
| Insufficient fixed points have been specified | The least-squares network adjustment cannot be made if not enough points have been specified as fixed - usually at least two fixed points are required |
| Insufficient station details ! Requires Inst Stn plus RO or Ref Bearing. Cannot process this page | Not enough data has been entered in the header section of the page or range of pages requested for processing - review the data and enter station details for the required pages, or check the range of pages required |
| Insufficient traverse observations to process | There is not enough data to compute a traverse - even one correct observation is sufficient |
| Invalid data - Page pp, Record nn - check entries | One or more essential fields are blank while other fields contain valid data in the numbered record on the indicated page of data selected for processing |
| Invalid data, Record 53, record type 4
Inst Stn: 205, Observing: 1567 HA: 125~42'15” Dist: 0.000 |
An observation with data outside the expected range of values has been read - it will be skipped (eg distance = zero) |
| Invalid Point Number ppp. Must be within range 1 to ppppp | An invalid point number (i.e. outside of the range 1-999999) was read during file input |
| Invalid point range | Valid point numbers are within the range 1-999999. They cannot be negative, zero or greater than 999999 |
| Is reflector tilting type ? | Geoida can make corrections for non-tilting reflectors - the effect of incorrectly specifying reflector type is greatest on the shortest lines |
| Meaning NOT applied to repeated obs at each instrumentation station (except any un-meaned F1/F2 observations) | The Mean Control Observations check-box is un-crossed to disable meaning of observations, but for any particular setup where observations made to the same point but on opposite faces are detected, these ARE meaned |
| No coords recorded or stored for Point pppp | The named point is an instrument station, backsight, traverse control point or similar but there are no details for the point stored in the database or read from the data. A dialog box which allows the user to enter these details is displayed following this prompt |
| No details for job Jobname | No details for the named job can be found - its database has probably been damaged |
| No fixed control points have been specified - correct and re-start (start point is sufficient for unclosed traverse) | A traverse or network cannot be processed until a minimum number of fixed control points have been specified. Eg, for a single traverse section requiring no adjustment, fixing the first station may be adequate |
| No jobs stored !! Check data area selected | A data area has been selected which does not contain any valid Geoida jobs |
| No model for Geoid-Spheroid Separation has been formed - Continue? | In Job Configuration the Geoid-spheroid separation item Apply to obs has been crossed to imply that interpolation of N-values, using the indicated Interpolation Method, is required for reduction of observations to spheroid, but no model exists. Either form the model or set up the geoid data first, or uncross the Apply to obs check box |
| No Radiation headers found - no data | No headers can be found for the radiation data selected for processing - the database table has probably been damaged |
| NO repeated obs at each instrumentation station were found - no meaned obs | The Mean Control Observations check-box was crossed to enable meaning of observations, but at each setup there were NO repeated observations found to mean, i.e. each point was observed once only on a single face |
| No traverse lines found | There is no traverse data to process or the data does not contain a traverse - would typically apply to SDR data collected by Topo program only |
| Point number 0 is invalid | Point numbers must be greater than 0 and within the range 1-999999. A point number of zero cannot be used |
| Point number ppp outside of range 1-ppppp !! Not stored | Point numbers must be greater than 0 and within the range 1-999999 - points outside of this range cannot be stored in the database |
| Radiations by Coordinate Program ... Use points from data as computed by SDR ? (Answer NO to reduce actual observations) | SDR observations have been collected by the Coordinate program which stores coordinates computed by the SDR as well as the raw observations from which they were derived. Geoida can read the coordinates directly, or re-compute them from the raw data |
| ReadJobDetails : Job Jobname does not exist | This condition may occur when Geoida is started after the files for the current Geoida job have been deleted or moved from the data area |
| Reference point pppp is not stored in Database - use the backbearing of value ddd.mmss from data ? | Radiations option - The named point has been specified as the backsight at a new setup but details for the point are not stored in the database so a bearing cannot be computed between it and the instrument station. However, a back-bearing has already been calculated from previous observations and may be used instead |
| Reference point pppp is not stored in Database - use the backbearing of value ddd.mmss from data file ? | SDR data - The named point has been specified as the backsight at a new setup but coordinate details for the point are not stored in the database so a bearing cannot be computed between it and the instrument station. However, a back-bearing is recorded in the data file and may be used instead |
| Selected file Filename does not exist | The file of the indicated name does not exist. If the filename was typed by the user, check the spelling of the filename, the path selected, and that no illegal characters have been used such as * ? + < > | [ ] \ / , ; : ” +. To avoid the possibility of typing errors etc, it is preferable to choose the file by selection from the list |
| Selected projection not found | The projection selected has not been found on a subsequent search of the library - check all projection entries |
| Skipping record type xx (not processed) | This record type may be invalid (eg bad data) or is a type not processed by Geoida - it will be skipped |
| Spheroid for this Projection is invalid | The spheroid specified for the current projection has not been found during a search of the library - check spheroid and projection entries |
| Standard Deviation cannot be zero - resetting to .01 - Distance obs nn (or) Angle obs nn | The particular observation has a standard deviation set to zero which is invalid. Geoida automatically resets this (the first) and all subsequent zero values to the value indicated which (normally) will constrain the observation during adjustment |
| Control observations have been extracted from the processed
data and written to Extract file < ….. >.
You may later edit and process the observations in this file using the 'Process Extracted Observations' option. Continue processing with the current option? |
If traverse or network observations require editing or re-ordering before further processing the Extract file, the user may break at this point and return to the menu. Otherwise continue to process the data as currently extracted |
| Unknown record type xx (not processed) | This record type may be invalid (eg bad data) or is a type not processed by Geoida - it will be skipped |
| WARNING - 21 reverse VCs with same sign as forward VCs were
found (should be opposites)
View log file for locations and check original data |
During the process of sorting and meaning traverse/network observations, Geoida searches for a distance or VC observation made in a reverse direction along the same line as the current line to mean with the current observation as a reciprocal to eliminate atmospheric and curvature effects. If such an observation is located, Geoida expects it to be either a complimentary vertical angle or a VC of opposite sign as would be reasonable for a reciprocal observation except for nearly horizontal lines where atmospheric effects may render the forward and reverse observations to be the same sign. The affected observations will be highlighted in the log file, and the user should investigate the reason for the inconsistency - for lines that are NOT near horizontal, serious instrumental, observational or data entry errors are indicated |
| WARNING - Fixed points have been modified since the geoid model was formed !! If the Geoid-Spheroid Separation values were included in the changes, you should re-form the model before proceeding to avoid interpolation errors with un-fixed points. Do you wish to continue ? | A fixed point used in the geoid model has been modified. If the N-value or the horizontal position was changed then errors will result in any subsequent N-value interpolations unless the model is reformed first |
| WARNING - Insufficient points to adjust on Section nn | A traverse section must have at least 1 unfixed point or 2 traverse legs before it can be adjusted. Check that observations have been entered or recorded correctly |
| WARNING - There may be insufficient memory to process traverse | The number of traverse or network observations that may be processed is limited only by the available memory. If other applications are currently loaded, close them to make more memory available |
| WARNING - traverse length of Section nn is zero - no adjustment | The sum of traverse distances in the current section is zero. Check that observations have been entered or recorded correctly |
| Converted from CHM to HTML with chm2web Standard 2.85 (unicode) |